Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16c1c90e956d231a3a561890d91545e7776236b8df7efcec4c7773f5e85882e6

Tx prefix hash: 8e80abac204bd782352e5676c0a5ffdeb00dccd1008600d9bf66313c441f4ea8
Tx public key: a79ded764fd6e44488aa3399b5cada694caffb0cb5f099762bdb214a5b5b90bf
Timestamp: 1730324184 Timestamp [UCT]: 2024-10-30 21:36:24 Age [y:d:h:m:s]: 00:025:03:51:38
Block: 1143077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17992 RingCT/type: yes/0
Extra: 01a79ded764fd6e44488aa3399b5cada694caffb0cb5f099762bdb214a5b5b90bf021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31757cf823786c06d90422f9cfaf4942b0d39d78d851311e92828448df8d9122 0.600000000000 1626936 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": 1143087, "vin": [ { "gen": { "height": 1143077 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31757cf823786c06d90422f9cfaf4942b0d39d78d851311e92828448df8d9122" } } ], "extra": [ 1, 167, 157, 237, 118, 79, 214, 228, 68, 136, 170, 51, 153, 181, 202, 218, 105, 76, 175, 251, 12, 181, 240, 153, 118, 43, 219, 33, 74, 91, 91, 144, 191, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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