Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6c0ea660cb9d862e7516aaf09ec29ec10346fc72adf04e3416ab5fb3d508265

Tx prefix hash: a91856cc2e73b8cfc656d52d26f09c61287c2b5b27218a4b67e138772d8eb157
Tx public key: e21e68f124ba60995cfc2740f536504d9bd864a8fbd1e87a6e0c5444e4ba9f85
Timestamp: 1718436701 Timestamp [UCT]: 2024-06-15 07:31:41 Age [y:d:h:m:s]: 00:222:17:21:12
Block: 1044608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159332 RingCT/type: yes/0
Extra: 01e21e68f124ba60995cfc2740f536504d9bd864a8fbd1e87a6e0c5444e4ba9f8502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d877d1dc86e80279650e565b2c9d1305ff596437a2badf39913ab5916d83d89 0.600000000000 1513959 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": 1044618, "vin": [ { "gen": { "height": 1044608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d877d1dc86e80279650e565b2c9d1305ff596437a2badf39913ab5916d83d89" } } ], "extra": [ 1, 226, 30, 104, 241, 36, 186, 96, 153, 92, 252, 39, 64, 245, 54, 80, 77, 155, 216, 100, 168, 251, 209, 232, 122, 110, 12, 84, 68, 228, 186, 159, 133, 2, 17, 0, 0, 0, 1, 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