Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 589da201844224d0ce9020d86cc2bdfc157c57440badf91932ae226e2e2114ae

Tx prefix hash: ef16b52680360028ed2745616ca4e4d7f28be8b3829e6488aea318c8f130616e
Tx public key: 5beb194db93c84e2573390a3f8ff32e82ae679c3a2f5faaab5a05ef32d97fddd
Timestamp: 1749749888 Timestamp [UCT]: 2025-06-12 17:38:08 Age [y:d:h:m:s]: 00:156:08:50:02
Block: 1303591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109488 RingCT/type: yes/0
Extra: 015beb194db93c84e2573390a3f8ff32e82ae679c3a2f5faaab5a05ef32d97fddd021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dabebc17c7749ce86eaeb0246a147deb26454348be54a351ce4e8cb8be1a520 0.600000000000 1791174 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": 1303601, "vin": [ { "gen": { "height": 1303591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dabebc17c7749ce86eaeb0246a147deb26454348be54a351ce4e8cb8be1a520" } } ], "extra": [ 1, 91, 235, 25, 77, 185, 60, 132, 226, 87, 51, 144, 163, 248, 255, 50, 232, 42, 230, 121, 195, 162, 245, 250, 170, 181, 160, 94, 243, 45, 151, 253, 221, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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