Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79efa8ca4e3bdef1a02d187b38ec12c1743e99eebc69f963c02fb523dba18fa6

Tx prefix hash: dd6644ea6a463d7c6dc928e3e49eaf450aeee0fec39f87a39aa47290e5803e88
Tx public key: 0a0ed2b1e3bfa7a75fa36f7ac779319e8c3b8bd5b13efedf958d02800edbabdb
Timestamp: 1587533405 Timestamp [UCT]: 2020-04-22 05:30:05 Age [y:d:h:m:s]: 05:019:13:05:40
Block: 94682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1185371 RingCT/type: yes/0
Extra: 010a0ed2b1e3bfa7a75fa36f7ac779319e8c3b8bd5b13efedf958d02800edbabdb0211000000024ac5aa02000000000000000000

1 output(s) for total of 298.043735751000 dcy

stealth address amount amount idx
00: 5d1ef3f4ae3d92830ea967d4650ac91989074a49313f62ff83908897de7a80fb 298.043735751000 168514 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": 94692, "vin": [ { "gen": { "height": 94682 } } ], "vout": [ { "amount": 298043735751, "target": { "key": "5d1ef3f4ae3d92830ea967d4650ac91989074a49313f62ff83908897de7a80fb" } } ], "extra": [ 1, 10, 14, 210, 177, 227, 191, 167, 167, 95, 163, 111, 122, 199, 121, 49, 158, 140, 59, 139, 213, 177, 62, 254, 223, 149, 141, 2, 128, 14, 219, 171, 219, 2, 17, 0, 0, 0, 2, 74, 197, 170, 2, 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