Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d8ea87c724f9c4abc911ac380503480f5d5f3d8a202156b16e26fe2cb574a37

Tx prefix hash: 27104a49700fe106482c1038fa479a4bd4958e7bdb34cb71bd97c1ccab75dc36
Tx public key: 34d6d8d384e1d0548fea04b793624a6bf4ca97c55a3dd5dfa265b9eabf070cc7
Timestamp: 1725627158 Timestamp [UCT]: 2024-09-06 12:52:38 Age [y:d:h:m:s]: 00:170:01:33:42
Block: 1104215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121337 RingCT/type: yes/0
Extra: 0134d6d8d384e1d0548fea04b793624a6bf4ca97c55a3dd5dfa265b9eabf070cc702110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44316a3f7ecbc00d0b1cd586fda0d6e1ebee8d1c1020334db3643c78ec214817 0.600000000000 1581294 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": 1104225, "vin": [ { "gen": { "height": 1104215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44316a3f7ecbc00d0b1cd586fda0d6e1ebee8d1c1020334db3643c78ec214817" } } ], "extra": [ 1, 52, 214, 216, 211, 132, 225, 208, 84, 143, 234, 4, 183, 147, 98, 74, 107, 244, 202, 151, 197, 90, 61, 213, 223, 162, 101, 185, 234, 191, 7, 12, 199, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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