Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfe8ad36af515419646518aa62d8461ccb49fbd986ae1786dece5a7b7bcf3bb4

Tx prefix hash: 722a028aeb06aeaaefb6bb1efdf3c01c47399d0b72dbf1b3405754b01e0ad594
Tx public key: c261938db9d182f31ee0b0255ede6867d3d538698a823c53d03cfc4413e53d82
Timestamp: 1578849120 Timestamp [UCT]: 2020-01-12 17:12:00 Age [y:d:h:m:s]: 05:028:19:34:50
Block: 44112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1170688 RingCT/type: yes/0
Extra: 01c261938db9d182f31ee0b0255ede6867d3d538698a823c53d03cfc4413e53d820211000000024943cd9f000000000000000000

1 output(s) for total of 438.368635763000 dcy

stealth address amount amount idx
00: 46993229cf44f99e86889640fe9b823ea646621a6bd146c0eb0a6497f4a7e5c1 438.368635763000 80164 of 0

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": 44122, "vin": [ { "gen": { "height": 44112 } } ], "vout": [ { "amount": 438368635763, "target": { "key": "46993229cf44f99e86889640fe9b823ea646621a6bd146c0eb0a6497f4a7e5c1" } } ], "extra": [ 1, 194, 97, 147, 141, 185, 209, 130, 243, 30, 224, 176, 37, 94, 222, 104, 103, 211, 213, 56, 105, 138, 130, 60, 83, 208, 60, 252, 68, 19, 229, 61, 130, 2, 17, 0, 0, 0, 2, 73, 67, 205, 159, 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