Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4e268b0b17fcef5d0dee09dd752c0820255cfadb4523723c14f6f99b81ad584e

Tx prefix hash: 19acf344605030f2e54350f24b20151a8b9aee2a4371773e0d517ebb67ca12a0
Tx public key: a9fd6defe6aefe022507070128a3266f16251ffec0e37dad665bb7f9cb9fee98
Timestamp: 1713461253 Timestamp [UCT]: 2024-04-18 17:27:33 Age [y:d:h:m:s]: 01:196:04:43:03
Block: 1003331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398883 RingCT/type: yes/0
Extra: 01a9fd6defe6aefe022507070128a3266f16251ffec0e37dad665bb7f9cb9fee9802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10f47b4c05a590dc84dcd8a3cdbe57856f0f434096d4b15ba5c97af2f3b124df 0.600000000000 1463861 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1003341, "vin": [ { "gen": { "height": 1003331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10f47b4c05a590dc84dcd8a3cdbe57856f0f434096d4b15ba5c97af2f3b124df" } } ], "extra": [ 1, 169, 253, 109, 239, 230, 174, 254, 2, 37, 7, 7, 1, 40, 163, 38, 111, 22, 37, 31, 254, 192, 227, 125, 173, 102, 91, 183, 249, 203, 159, 238, 152, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8