Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01ea6efe2a508b29ccf0ec33387d412a94aa08f5a2bc12c07f7e53665e0014d1

Tx prefix hash: 4dea480fb3fe9813753b04ac0fbe9c7d74b8111f519df11f8d423cf3abd4e58b
Tx public key: 1852488b3c31427fba43b5cf0a091537a2d8c4121ad47dcd059905a9e9916207
Timestamp: 1736533083 Timestamp [UCT]: 2025-01-10 18:18:03 Age [y:d:h:m:s]: 00:294:00:31:24
Block: 1194482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207634 RingCT/type: yes/0
Extra: 011852488b3c31427fba43b5cf0a091537a2d8c4121ad47dcd059905a9e99162070211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5038b90a5f8c3a2e6fb8ba5a7c76a0a5f0cdc5252c6b37bf153e2adfe9a2b49 0.600000000000 1681053 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": 1194492, "vin": [ { "gen": { "height": 1194482 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5038b90a5f8c3a2e6fb8ba5a7c76a0a5f0cdc5252c6b37bf153e2adfe9a2b49" } } ], "extra": [ 1, 24, 82, 72, 139, 60, 49, 66, 127, 186, 67, 181, 207, 10, 9, 21, 55, 162, 216, 196, 18, 26, 212, 125, 205, 5, 153, 5, 169, 233, 145, 98, 7, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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