Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6d774cfd0997f21a20efc6ca79521a155514a2ca882564e7459cfa76f56d3aa

Tx prefix hash: f2f7c2ee6b73260f804293e0b5b1b619527792af051dc93460905eee2526a964
Tx public key: 644f2ebe68f51fd3b1a1135ea25c9476c2a99c853c88ba6b8475a34d79d1c4b2
Timestamp: 1713687268 Timestamp [UCT]: 2024-04-21 08:14:28 Age [y:d:h:m:s]: 00:203:21:00:35
Block: 1005210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145948 RingCT/type: yes/0
Extra: 01644f2ebe68f51fd3b1a1135ea25c9476c2a99c853c88ba6b8475a34d79d1c4b20211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b4d5b8876f61100ea5c9ce2287c26bf4bf16c99c18201da98cc68d830019ae9 0.600000000000 1465794 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": 1005220, "vin": [ { "gen": { "height": 1005210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b4d5b8876f61100ea5c9ce2287c26bf4bf16c99c18201da98cc68d830019ae9" } } ], "extra": [ 1, 100, 79, 46, 190, 104, 245, 31, 211, 177, 161, 19, 94, 162, 92, 148, 118, 194, 169, 156, 133, 60, 136, 186, 107, 132, 117, 163, 77, 121, 209, 196, 178, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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