Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbb437a7404f46d05c434f2ce44f703974e0edb542aa02ebfdb1d46cb557c991

Tx prefix hash: f611494778a00a9f559b514f48215fc19b6070f15cdca5512a74773ec9a9f1f9
Tx public key: bf2771daf9eda3a341dd13f3ae8fb4d25f74c60f9e789547f3cae1390044a3ac
Timestamp: 1578176557 Timestamp [UCT]: 2020-01-04 22:22:37 Age [y:d:h:m:s]: 05:305:02:18:17
Block: 38828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1365599 RingCT/type: yes/0
Extra: 01bf2771daf9eda3a341dd13f3ae8fb4d25f74c60f9e789547f3cae1390044a3ac021100000052bd0f9f9f000000000000000000

1 output(s) for total of 456.409899644000 dcy

stealth address amount amount idx
00: 855e0a8218878d76f2a215bd3ef6905f46871c2930f612ffff9cc427ad626d5c 456.409899644000 66493 of 0

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": 38838, "vin": [ { "gen": { "height": 38828 } } ], "vout": [ { "amount": 456409899644, "target": { "key": "855e0a8218878d76f2a215bd3ef6905f46871c2930f612ffff9cc427ad626d5c" } } ], "extra": [ 1, 191, 39, 113, 218, 249, 237, 163, 163, 65, 221, 19, 243, 174, 143, 180, 210, 95, 116, 198, 15, 158, 120, 149, 71, 243, 202, 225, 57, 0, 68, 163, 172, 2, 17, 0, 0, 0, 82, 189, 15, 159, 159, 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