Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 437cab7461c66a572d938606a6b0c548c56f792d55451cdec1e3140c898ae930

Tx prefix hash: a26c84c5d2bd9abd6d0ae8305216dc7a9550460307fea240f681c8df81270bfc
Tx public key: 1228f92cfe1a62c8f4e39d1ab4a04f624c3fd6bd47e416e33fe8480b8194efc5
Timestamp: 1733385520 Timestamp [UCT]: 2024-12-05 07:58:40 Age [y:d:h:m:s]: 00:133:11:24:14
Block: 1168430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95186 RingCT/type: yes/0
Extra: 011228f92cfe1a62c8f4e39d1ab4a04f624c3fd6bd47e416e33fe8480b8194efc5021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f30e724a38acb5d3813d604515b9509d7f3224a013927b4d4120021dfb328bb 0.600000000000 1654139 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": 1168440, "vin": [ { "gen": { "height": 1168430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f30e724a38acb5d3813d604515b9509d7f3224a013927b4d4120021dfb328bb" } } ], "extra": [ 1, 18, 40, 249, 44, 254, 26, 98, 200, 244, 227, 157, 26, 180, 160, 79, 98, 76, 63, 214, 189, 71, 228, 22, 227, 63, 232, 72, 11, 129, 148, 239, 197, 2, 17, 0, 0, 0, 5, 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