Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 372a4c093ffbd7a364ee72078c9b7089ee1bc24f7d6c94a17dcb2987b38dce23

Tx prefix hash: feafee358b732d14c776b5fa53c81363f9f1e40c37b5b4699d40c9c6431e609a
Tx public key: a3323f0b0cb389c7bf2a6ee814d77a0aa8fef1223376e84bafc732b2a758aad3
Timestamp: 1725714244 Timestamp [UCT]: 2024-09-07 13:04:04 Age [y:d:h:m:s]: 01:061:21:24:25
Block: 1104938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302649 RingCT/type: yes/0
Extra: 01a3323f0b0cb389c7bf2a6ee814d77a0aa8fef1223376e84bafc732b2a758aad3021100000008e914dd15000000000000000000

1 output(s) for total of 0.607980000000 dcy

stealth address amount amount idx
00: d9b2922d3837c79bf20d949b7f34f9039a48bc8dc9ec1cabb2c8240ca312cd0e 0.607980000000 1582265 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": 1104948, "vin": [ { "gen": { "height": 1104938 } } ], "vout": [ { "amount": 607980000, "target": { "key": "d9b2922d3837c79bf20d949b7f34f9039a48bc8dc9ec1cabb2c8240ca312cd0e" } } ], "extra": [ 1, 163, 50, 63, 11, 12, 179, 137, 199, 191, 42, 110, 232, 20, 215, 122, 10, 168, 254, 241, 34, 51, 118, 232, 75, 175, 199, 50, 178, 167, 88, 170, 211, 2, 17, 0, 0, 0, 8, 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