Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d64b782cfb1845249a9c6886054fc319ee293db3b8866461eceb14d31f4f5d79

Tx prefix hash: e991c859441a17eca249f53f1b882f2bea0cbb738a7bae12776fd0fc9c8a69a9
Tx public key: 92130b0c5445d6f12e05edc83bf1ffbf79b1991f9e876b5a4935da8acd85b9ea
Timestamp: 1704480166 Timestamp [UCT]: 2024-01-05 18:42:46 Age [y:d:h:m:s]: 01:121:08:41:56
Block: 928878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347865 RingCT/type: yes/0
Extra: 0192130b0c5445d6f12e05edc83bf1ffbf79b1991f9e876b5a4935da8acd85b9ea0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5854241acd0c48ddb89bb11d333c5710f6d76946b5f207209a56c396fe9a8500 0.600000000000 1386742 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": 928888, "vin": [ { "gen": { "height": 928878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5854241acd0c48ddb89bb11d333c5710f6d76946b5f207209a56c396fe9a8500" } } ], "extra": [ 1, 146, 19, 11, 12, 84, 69, 214, 241, 46, 5, 237, 200, 59, 241, 255, 191, 121, 177, 153, 31, 158, 135, 107, 90, 73, 53, 218, 138, 205, 133, 185, 234, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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