Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a87993aa675c4dcd28d0f63f8fef9284aa060e03d9842f67342659b19eaa563

Tx prefix hash: e90186c6687dfb50c96292abad0afa0cdad7b9429d7da59b3e3fc66d5d7e615e
Tx public key: 822db34c47343e332958a12bbd406232832b16da10ab74a33c07b9d5f9560cab
Timestamp: 1699410079 Timestamp [UCT]: 2023-11-08 02:21:19 Age [y:d:h:m:s]: 01:075:21:39:54
Block: 886858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315622 RingCT/type: yes/0
Extra: 01822db34c47343e332958a12bbd406232832b16da10ab74a33c07b9d5f9560cab02110000000233af99f4000000000000000000

1 output(s) for total of 0.707084466000 dcy

stealth address amount amount idx
00: c13a0e75a5c608ae10b3f6ef7d5a17e562295210f80cc252e48f84aec8da8667 0.707084466000 1342705 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": 886868, "vin": [ { "gen": { "height": 886858 } } ], "vout": [ { "amount": 707084466, "target": { "key": "c13a0e75a5c608ae10b3f6ef7d5a17e562295210f80cc252e48f84aec8da8667" } } ], "extra": [ 1, 130, 45, 179, 76, 71, 52, 62, 51, 41, 88, 161, 43, 189, 64, 98, 50, 131, 43, 22, 218, 16, 171, 116, 163, 60, 7, 185, 213, 249, 86, 12, 171, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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