Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d46f14cc685ef20ce54d890669268a125c2af4bb1defe0dacd866d0cb6754fa

Tx prefix hash: 8a99284d82def8e4683e653f071e84d0af476fbbe63caf5a91ee8aa44789bd78
Tx public key: 7c485b9ca763f22a6d1fd9ca29b28117a3659e7cb77817a3cba4c5051155e801
Timestamp: 1727684973 Timestamp [UCT]: 2024-09-30 08:29:33 Age [y:d:h:m:s]: 00:114:10:45:48
Block: 1121272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81778 RingCT/type: yes/0
Extra: 017c485b9ca763f22a6d1fd9ca29b28117a3659e7cb77817a3cba4c5051155e801021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1cbc6940f71931c0b87c13e6ee7ff5246b8c1206decbe9ff66cdf1cb5ba888d 0.600000000000 1603487 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": 1121282, "vin": [ { "gen": { "height": 1121272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1cbc6940f71931c0b87c13e6ee7ff5246b8c1206decbe9ff66cdf1cb5ba888d" } } ], "extra": [ 1, 124, 72, 91, 156, 167, 99, 242, 42, 109, 31, 217, 202, 41, 178, 129, 23, 163, 101, 158, 124, 183, 120, 23, 163, 203, 164, 197, 5, 17, 85, 232, 1, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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