Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f72456d6fc7c78eb46f692601790961e10d40e3cd3fe9b6c30c6fc91ab2fd99b

Tx prefix hash: ddc489827daa4fcb03113cf2760eb39441d61fd7a22e62bc10a4fd26389c754c
Tx public key: 105ab169917f4e43c1c3bf11f74b09e9105907c2221acd86319b720aa4317d31
Timestamp: 1688718907 Timestamp [UCT]: 2023-07-07 08:35:07 Age [y:d:h:m:s]: 01:346:00:47:59
Block: 798477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508377 RingCT/type: yes/0
Extra: 01105ab169917f4e43c1c3bf11f74b09e9105907c2221acd86319b720aa4317d31021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.387760007000 dcy

stealth address amount amount idx
00: eb1d339a208e2b4d10e00e5759225c0d2a102cf57f738317727de5d1e8aeab3a 1.387760007000 1249414 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": 798487, "vin": [ { "gen": { "height": 798477 } } ], "vout": [ { "amount": 1387760007, "target": { "key": "eb1d339a208e2b4d10e00e5759225c0d2a102cf57f738317727de5d1e8aeab3a" } } ], "extra": [ 1, 16, 90, 177, 105, 145, 127, 78, 67, 193, 195, 191, 17, 247, 75, 9, 233, 16, 89, 7, 194, 34, 26, 205, 134, 49, 155, 114, 10, 164, 49, 125, 49, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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