Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa1e8ab6c5cb6dbdd655a99108b4b33db0d8173dfa379ef16fcf4896be57287a

Tx prefix hash: 40c9ffa2168bb4eb6b014f96cb8da60ec920c94552012dc52affcde97dbbcda5
Tx public key: d7ee9bada6ce93c31f1e9c625c221c282d1b30635e153a46ff4a3f172fe80acc
Timestamp: 1577033606 Timestamp [UCT]: 2019-12-22 16:53:26 Age [y:d:h:m:s]: 05:015:09:41:26
Block: 29684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1160764 RingCT/type: yes/0
Extra: 01d7ee9bada6ce93c31f1e9c625c221c282d1b30635e153a46ff4a3f172fe80acc02110000001dd81c26c0000000000000000000

1 output(s) for total of 489.379134270000 dcy

stealth address amount amount idx
00: 3c9dd969a58d68d10766ab18fffa5c5ef593528b0bdade2065cd915647a428dc 489.379134270000 48864 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": 29694, "vin": [ { "gen": { "height": 29684 } } ], "vout": [ { "amount": 489379134270, "target": { "key": "3c9dd969a58d68d10766ab18fffa5c5ef593528b0bdade2065cd915647a428dc" } } ], "extra": [ 1, 215, 238, 155, 173, 166, 206, 147, 195, 31, 30, 156, 98, 92, 34, 28, 40, 45, 27, 48, 99, 94, 21, 58, 70, 255, 74, 63, 23, 47, 232, 10, 204, 2, 17, 0, 0, 0, 29, 216, 28, 38, 192, 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