Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4470816f79cb639a8715f3a871225f6d493b651dca6275dd42f866880fb1184

Tx prefix hash: cff0d4340cf7e56a8356c6747dc53dc4d664d45c77aa0c8431ab288d054c15ab
Tx public key: 8ba8a53cba2a168f0181f2068be80229ea82b6dd4f9642bc03c6231ae6a0fa02
Timestamp: 1735180857 Timestamp [UCT]: 2024-12-26 02:40:57 Age [y:d:h:m:s]: 00:088:00:25:34
Block: 1183296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62673 RingCT/type: yes/0
Extra: 018ba8a53cba2a168f0181f2068be80229ea82b6dd4f9642bc03c6231ae6a0fa02021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f04550579c82a0cb5fe295212d4c4d32f1b505556a70fd145e8401b59d7299b1 0.600000000000 1669739 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": 1183306, "vin": [ { "gen": { "height": 1183296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f04550579c82a0cb5fe295212d4c4d32f1b505556a70fd145e8401b59d7299b1" } } ], "extra": [ 1, 139, 168, 165, 60, 186, 42, 22, 143, 1, 129, 242, 6, 139, 232, 2, 41, 234, 130, 182, 221, 79, 150, 66, 188, 3, 198, 35, 26, 230, 160, 250, 2, 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