Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25a68dc172fc1ed6be332cbe8a54e8194921552cd72479ac5059bd4366efae34

Tx prefix hash: 34583cbb602af6c622fa737d5d1e1eeb1c82195fd997af8d1db6f43e6cb25d7a
Tx public key: 31f17f7a1bd18d76907db536d00cff132af7af021afc4f98a7519c6cdb8f4d3d
Timestamp: 1714798172 Timestamp [UCT]: 2024-05-04 04:49:32 Age [y:d:h:m:s]: 01:189:06:48:44
Block: 1014436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393905 RingCT/type: yes/0
Extra: 0131f17f7a1bd18d76907db536d00cff132af7af021afc4f98a7519c6cdb8f4d3d0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad5d64e2c8b1571f0667a4186aa483c38927aaafd3943506c5dad9a8da93a849 0.600000000000 1477529 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": 1014446, "vin": [ { "gen": { "height": 1014436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad5d64e2c8b1571f0667a4186aa483c38927aaafd3943506c5dad9a8da93a849" } } ], "extra": [ 1, 49, 241, 127, 122, 27, 209, 141, 118, 144, 125, 181, 54, 208, 12, 255, 19, 42, 247, 175, 2, 26, 252, 79, 152, 167, 81, 156, 108, 219, 143, 77, 61, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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