Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32f3ae4c47f5bf16da822b64c45a56a3b6a5fa09a7f05e1a33d7d7444f39bbda

Tx prefix hash: 269eb933759f02ac35e8d57113ae743fb1245e9b2fcbbc940e3a5dcd7d1befe4
Tx public key: 53d13fdfd693f6013d83de0afecb59583cd2c0e584f839c6aa73ed5c398150c6
Timestamp: 1723076225 Timestamp [UCT]: 2024-08-08 00:17:05 Age [y:d:h:m:s]: 00:272:08:32:57
Block: 1083055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194564 RingCT/type: yes/0
Extra: 0153d13fdfd693f6013d83de0afecb59583cd2c0e584f839c6aa73ed5c398150c6021100000001341001ae000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 740cb82f532b265eef2eb894282826f74ff6500a66e3ba3b74d843576351f617 0.600000000000 1556890 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": 1083065, "vin": [ { "gen": { "height": 1083055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "740cb82f532b265eef2eb894282826f74ff6500a66e3ba3b74d843576351f617" } } ], "extra": [ 1, 83, 209, 63, 223, 214, 147, 246, 1, 61, 131, 222, 10, 254, 203, 89, 88, 60, 210, 192, 229, 132, 248, 57, 198, 170, 115, 237, 92, 57, 129, 80, 198, 2, 17, 0, 0, 0, 1, 52, 16, 1, 174, 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