Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fc655ab9c959ee1e5724a1414541d1095075bac8e6762c97c69c40ab4f33330

Tx prefix hash: 8bee7af56e95c696ae57cd504ad3fba7970de0901713c076111d9acded0f09f3
Tx public key: 865fba16e8b92342b947f317e4f6df4b5cfdb575e30400f03b925dfdfe77ec89
Timestamp: 1717941367 Timestamp [UCT]: 2024-06-09 13:56:07 Age [y:d:h:m:s]: 00:283:04:02:42
Block: 1040488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202375 RingCT/type: yes/0
Extra: 01865fba16e8b92342b947f317e4f6df4b5cfdb575e30400f03b925dfdfe77ec8902110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa6cd840a5ec918db7fbfea7e7483f0cb75208d1ff18b133c098c4165cd49c78 0.600000000000 1509145 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": 1040498, "vin": [ { "gen": { "height": 1040488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa6cd840a5ec918db7fbfea7e7483f0cb75208d1ff18b133c098c4165cd49c78" } } ], "extra": [ 1, 134, 95, 186, 22, 232, 185, 35, 66, 185, 71, 243, 23, 228, 246, 223, 75, 92, 253, 181, 117, 227, 4, 0, 240, 59, 146, 93, 253, 254, 119, 236, 137, 2, 17, 0, 0, 0, 1, 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