Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5075da5660e7160e61aa5c9fd908db77ee5f8f3742164a2271bdcde606609114

Tx prefix hash: d630f660fc118138548ec905124fc94c7ce746afc95e2ff5abc763a2203beed9
Tx public key: 287a02f4ae4e7e1df8b38ce475e107bcfbe5c70f4975a86e5a92d9ca512ca9ee
Timestamp: 1729011335 Timestamp [UCT]: 2024-10-15 16:55:35 Age [y:d:h:m:s]: 00:149:05:40:13
Block: 1132266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106441 RingCT/type: yes/0
Extra: 01287a02f4ae4e7e1df8b38ce475e107bcfbe5c70f4975a86e5a92d9ca512ca9ee02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ae4a6756139becfdec64f72aaf5e611d34c3d6a60b05567bb163b8021ef72de 0.600000000000 1615179 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": 1132276, "vin": [ { "gen": { "height": 1132266 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ae4a6756139becfdec64f72aaf5e611d34c3d6a60b05567bb163b8021ef72de" } } ], "extra": [ 1, 40, 122, 2, 244, 174, 78, 126, 29, 248, 179, 140, 228, 117, 225, 7, 188, 251, 229, 199, 15, 73, 117, 168, 110, 90, 146, 217, 202, 81, 44, 169, 238, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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