Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b80656727933e82acd6d65972679723754c09906ede395d3f3889fe48e6c6286

Tx prefix hash: 63390b770306f8af1891b2200848ac5a2d7a79e6e99f1203c486e27d1882374b
Tx public key: dc49a7db5fe12d98b6f958e9f25d4d5ff892fa8e2ab8d73d983d2c4c1bb889e3
Timestamp: 1711201737 Timestamp [UCT]: 2024-03-23 13:48:57 Age [y:d:h:m:s]: 01:058:20:20:47
Block: 984639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303043 RingCT/type: yes/0
Extra: 01dc49a7db5fe12d98b6f958e9f25d4d5ff892fa8e2ab8d73d983d2c4c1bb889e302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0885c602f9a93b1cf1cbb666d0e7b9b16682a263007aecd9b9364c2bfc4ce209 0.600000000000 1444810 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": 984649, "vin": [ { "gen": { "height": 984639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0885c602f9a93b1cf1cbb666d0e7b9b16682a263007aecd9b9364c2bfc4ce209" } } ], "extra": [ 1, 220, 73, 167, 219, 95, 225, 45, 152, 182, 249, 88, 233, 242, 93, 77, 95, 248, 146, 250, 142, 42, 184, 215, 61, 152, 61, 44, 76, 27, 184, 137, 227, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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