Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95a67814f635a892493cade5bde72ec384bf39dccd8bdae04f617d316865adf5

Tx prefix hash: 34f0a0f6dbca59a217d79f873b1d2fba79888ee4c7d40db4c4cdf9b7cf390610
Tx public key: 32c41f5144d792a9e31811b61e9e8ff57c186e7bdf3b22cffee2979adfd05892
Timestamp: 1703500194 Timestamp [UCT]: 2023-12-25 10:29:54 Age [y:d:h:m:s]: 01:083:01:57:23
Block: 920760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320509 RingCT/type: yes/0
Extra: 0132c41f5144d792a9e31811b61e9e8ff57c186e7bdf3b22cffee2979adfd0589202110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ec36f5f1900f14bb5aab9362316daa291ed6a8ef5cfa7d00256072e700a1607 0.600000000000 1378444 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": 920770, "vin": [ { "gen": { "height": 920760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ec36f5f1900f14bb5aab9362316daa291ed6a8ef5cfa7d00256072e700a1607" } } ], "extra": [ 1, 50, 196, 31, 81, 68, 215, 146, 169, 227, 24, 17, 182, 30, 158, 143, 245, 124, 24, 110, 123, 223, 59, 34, 207, 254, 226, 151, 154, 223, 208, 88, 146, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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