Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc811d848163faaf04c0b5cc440dbcc13ec3747f3638902859dd64a4d9705450

Tx prefix hash: 7e5471dc08573e24b2c469811c415598a0e06df8d076fa42741a193099968a25
Tx public key: 0a4764d7a4d1e5037956d19fb1c00438ed78d2acfaf9c715a79ff748c4e449ea
Timestamp: 1679406305 Timestamp [UCT]: 2023-03-21 13:45:05 Age [y:d:h:m:s]: 02:020:08:28:57
Block: 721906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 536081 RingCT/type: yes/0
Extra: 010a4764d7a4d1e5037956d19fb1c00438ed78d2acfaf9c715a79ff748c4e449ea021100000002e6d27f9c000000000000000000

1 output(s) for total of 2.489004179000 dcy

stealth address amount amount idx
00: 559244763f90448fbe51d68f65f58506b99565de2743b4661ac5c1afd6021118 2.489004179000 1166795 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": 721916, "vin": [ { "gen": { "height": 721906 } } ], "vout": [ { "amount": 2489004179, "target": { "key": "559244763f90448fbe51d68f65f58506b99565de2743b4661ac5c1afd6021118" } } ], "extra": [ 1, 10, 71, 100, 215, 164, 209, 229, 3, 121, 86, 209, 159, 177, 192, 4, 56, 237, 120, 210, 172, 250, 249, 199, 21, 167, 159, 247, 72, 196, 228, 73, 234, 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