Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d001a18809ceb579ffaee51ea018e3aa994377896c07fe37cc5fb791e0ecdc2

Tx prefix hash: 30d33c7bcaf074b9d952c932abb1325b70d2f15a418de4b4c918cc6f836cc7e1
Tx public key: 454e1d98d44be89fabfb5ad09aa35fe61dddfb48f39bd6560ff638d3a73fdf92
Timestamp: 1730470428 Timestamp [UCT]: 2024-11-01 14:13:48 Age [y:d:h:m:s]: 00:144:15:21:39
Block: 1144274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103195 RingCT/type: yes/0
Extra: 01454e1d98d44be89fabfb5ad09aa35fe61dddfb48f39bd6560ff638d3a73fdf92021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2347b1b2ade6b960e02b10e103cb55ac81f5f383e71ecf4c951f2242294d1d8 0.600000000000 1628437 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": 1144284, "vin": [ { "gen": { "height": 1144274 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2347b1b2ade6b960e02b10e103cb55ac81f5f383e71ecf4c951f2242294d1d8" } } ], "extra": [ 1, 69, 78, 29, 152, 212, 75, 232, 159, 171, 251, 90, 208, 154, 163, 95, 230, 29, 221, 251, 72, 243, 155, 214, 86, 15, 246, 56, 211, 167, 63, 223, 146, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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