Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0889d5bd3e0a37d1131ea5e2e3921e8489c16ffd61d3bf35a1da73b5fd0a02ae

Tx prefix hash: b930599fcb87eab5c5d4df2c1b32077af7749c3139a906b780b74e556e55fb2d
Tx public key: ba06ac01a3cc01c6a268904dd3445479eb1edd046a7df3ea58d0ff1507f2c7b7
Timestamp: 1648444661 Timestamp [UCT]: 2022-03-28 05:17:41 Age [y:d:h:m:s]: 03:218:10:24:01
Block: 467986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 934033 RingCT/type: yes/0
Extra: 01ba06ac01a3cc01c6a268904dd3445479eb1edd046a7df3ea58d0ff1507f2c7b702110000000dc9067537000000000000000000

1 output(s) for total of 17.273023512000 dcy

stealth address amount amount idx
00: ccc611d0a5b61ce9719d146432489774c9b2e16b3794d824ee947c18bba8b580 17.273023512000 886608 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": 467996, "vin": [ { "gen": { "height": 467986 } } ], "vout": [ { "amount": 17273023512, "target": { "key": "ccc611d0a5b61ce9719d146432489774c9b2e16b3794d824ee947c18bba8b580" } } ], "extra": [ 1, 186, 6, 172, 1, 163, 204, 1, 198, 162, 104, 144, 77, 211, 68, 84, 121, 235, 30, 221, 4, 106, 125, 243, 234, 88, 208, 255, 21, 7, 242, 199, 183, 2, 17, 0, 0, 0, 13, 201, 6, 117, 55, 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