Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c133b9169b3b74b3413ebaba436beebba634fb12199cac0d3041d78cb5be7c54

Tx prefix hash: 08a35ea4f9e66e1a4f383cd9e90311acdf7d3afefd18e1f265f61a23dd638ce0
Tx public key: 5cae2c2b1ba81038f90c83d29be3693e0ef1d34a25fb11ba284885045437a1a2
Timestamp: 1738255451 Timestamp [UCT]: 2025-01-30 16:44:11 Age [y:d:h:m:s]: 00:136:17:13:52
Block: 1208481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97681 RingCT/type: yes/0
Extra: 015cae2c2b1ba81038f90c83d29be3693e0ef1d34a25fb11ba284885045437a1a20211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f04d91248f368f974b56bc6d97238d81ea73915f46975629e3dd7ba32536894 0.600000000000 1695214 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": 1208491, "vin": [ { "gen": { "height": 1208481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f04d91248f368f974b56bc6d97238d81ea73915f46975629e3dd7ba32536894" } } ], "extra": [ 1, 92, 174, 44, 43, 27, 168, 16, 56, 249, 12, 131, 210, 155, 227, 105, 62, 14, 241, 211, 74, 37, 251, 17, 186, 40, 72, 133, 4, 84, 55, 161, 162, 2, 17, 0, 0, 0, 6, 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