Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ee8084a5f480a74e593ece34165f8759abe18114fe0f42a185c0da2b669c40e

Tx prefix hash: 80ba2e8b77f96060961668cc3635dcdcf8f0dfacd91e86ea2a5b9794ad0aa24c
Tx public key: 754a19c8442a9946acfd64c00e39ad16bbd3f1d2b75c477c1d58bfc3386d2a81
Timestamp: 1713843369 Timestamp [UCT]: 2024-04-23 03:36:09 Age [y:d:h:m:s]: 01:190:21:20:24
Block: 1006514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395077 RingCT/type: yes/0
Extra: 01754a19c8442a9946acfd64c00e39ad16bbd3f1d2b75c477c1d58bfc3386d2a8102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df1ad65fa1a6e4ecc313ccd41a353b89b903dc11ed356f466c430f2fcb92f15a 0.600000000000 1467568 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": 1006524, "vin": [ { "gen": { "height": 1006514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df1ad65fa1a6e4ecc313ccd41a353b89b903dc11ed356f466c430f2fcb92f15a" } } ], "extra": [ 1, 117, 74, 25, 200, 68, 42, 153, 70, 172, 253, 100, 192, 14, 57, 173, 22, 187, 211, 241, 210, 183, 92, 71, 124, 29, 88, 191, 195, 56, 109, 42, 129, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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