Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93bafd2bcd6b70cf80235599e6bcaf1dd628058a3828e093c715ac26fb26f5e5

Tx prefix hash: 0ba391490055c28931336becd74b128969bb844fcc292513cb20f33751bdb387
Tx public key: 4cc477ff83d8d2a4a3ac4ad745e99003313cd7ee3d46aa1c288e20a04cca2b6d
Timestamp: 1724797319 Timestamp [UCT]: 2024-08-27 22:21:59 Age [y:d:h:m:s]: 00:089:00:40:38
Block: 1097312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63687 RingCT/type: yes/0
Extra: 014cc477ff83d8d2a4a3ac4ad745e99003313cd7ee3d46aa1c288e20a04cca2b6d02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd1bb1c8abd4f431229373456b3c4fb5b604dcaad457d2d6edcbb9ad50bce328 0.600000000000 1572693 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": 1097322, "vin": [ { "gen": { "height": 1097312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd1bb1c8abd4f431229373456b3c4fb5b604dcaad457d2d6edcbb9ad50bce328" } } ], "extra": [ 1, 76, 196, 119, 255, 131, 216, 210, 164, 163, 172, 74, 215, 69, 233, 144, 3, 49, 60, 215, 238, 61, 70, 170, 28, 40, 142, 32, 160, 76, 202, 43, 109, 2, 17, 0, 0, 0, 1, 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