Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3d470729fd7c60ac95f91e5dc4ffbd04d031229f33302396d0328fcfc6485a1

Tx prefix hash: 099ec63a6cc4d244fc1b09253973bb85e71bf8b7709d87790c57893c608aac6d
Tx public key: bc6ab4e24d4253e3f4513de1b7767e097984bfe6589e37f0adf71fe9cc29e41a
Timestamp: 1737565519 Timestamp [UCT]: 2025-01-22 17:05:19 Age [y:d:h:m:s]: 00:146:22:11:54
Block: 1202984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104746 RingCT/type: yes/0
Extra: 01bc6ab4e24d4253e3f4513de1b7767e097984bfe6589e37f0adf71fe9cc29e41a0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1b20404da2f9ec1bcf73d8a1a7dc43859f3689da4b50cbc844a9443fc2e1859 0.600000000000 1689655 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": 1202994, "vin": [ { "gen": { "height": 1202984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1b20404da2f9ec1bcf73d8a1a7dc43859f3689da4b50cbc844a9443fc2e1859" } } ], "extra": [ 1, 188, 106, 180, 226, 77, 66, 83, 227, 244, 81, 61, 225, 183, 118, 126, 9, 121, 132, 191, 230, 88, 158, 55, 240, 173, 247, 31, 233, 204, 41, 228, 26, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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