Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f77eecba6f304d32851155dc0fc71af6909a8b1cb2ae4b70e54a0bab17f114fe

Tx prefix hash: 10d11ba1c25a7be3a970d5ae05dfc2bbb29be2527c70b320fafb4f74550e4003
Tx public key: 785b16dc9906ca6816980fcd9869a9a40b7aebcea189f1ef1f1786d524fa4f54
Timestamp: 1637270653 Timestamp [UCT]: 2021-11-18 21:24:13 Age [y:d:h:m:s]: 03:014:08:25:57
Block: 377229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 788994 RingCT/type: yes/0
Extra: 01785b16dc9906ca6816980fcd9869a9a40b7aebcea189f1ef1f1786d524fa4f54021100000129b494d89c000000000000000000

1 output(s) for total of 34.521659200000 dcy

stealth address amount amount idx
00: 5707aea81cee117f12c412ceda26ff38172a7a7bf3a4a3e94ebfcdf782db690c 34.521659200000 763029 of 0

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": 377239, "vin": [ { "gen": { "height": 377229 } } ], "vout": [ { "amount": 34521659200, "target": { "key": "5707aea81cee117f12c412ceda26ff38172a7a7bf3a4a3e94ebfcdf782db690c" } } ], "extra": [ 1, 120, 91, 22, 220, 153, 6, 202, 104, 22, 152, 15, 205, 152, 105, 169, 164, 11, 122, 235, 206, 161, 137, 241, 239, 31, 23, 134, 213, 36, 250, 79, 84, 2, 17, 0, 0, 1, 41, 180, 148, 216, 156, 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