Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6aa11d3429f0a643a98cd18337ef5c01f666c592a2bf0232fabe9816f7664f75

Tx prefix hash: 2a8e3176e6671a73a385ebdf2b747ab7c18f0153edc0fe8d8abc006002189f1d
Tx public key: 5ae501f88698c93efcc3f270e56a2f9e180000cc4bc6dea592d0fa91b9d1f9dd
Timestamp: 1720550306 Timestamp [UCT]: 2024-07-09 18:38:26 Age [y:d:h:m:s]: 01:118:10:42:32
Block: 1062130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343143 RingCT/type: yes/0
Extra: 015ae501f88698c93efcc3f270e56a2f9e180000cc4bc6dea592d0fa91b9d1f9dd02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbfd94f6e4c92ea44c4a85663d24dbaca46db4387bebd7c684ee5060d8497a64 0.600000000000 1532631 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": 1062140, "vin": [ { "gen": { "height": 1062130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbfd94f6e4c92ea44c4a85663d24dbaca46db4387bebd7c684ee5060d8497a64" } } ], "extra": [ 1, 90, 229, 1, 248, 134, 152, 201, 62, 252, 195, 242, 112, 229, 106, 47, 158, 24, 0, 0, 204, 75, 198, 222, 165, 146, 208, 250, 145, 185, 209, 249, 221, 2, 17, 0, 0, 0, 2, 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