Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70df508070c03bf263f981d77919386311e4eb9d6aa5388bb97b2e375f262bb7

Tx prefix hash: f7d3fb74069ed9116aa1b190d6157c641505f282adb9d3be144d297be43989d1
Tx public key: 1c75daf566f95fc88db3ff37fcec6b6affc49f288b0f7e3b1d8aebd40475f9c9
Timestamp: 1706402668 Timestamp [UCT]: 2024-01-28 00:44:28 Age [y:d:h:m:s]: 00:301:00:43:54
Block: 944800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215558 RingCT/type: yes/0
Extra: 011c75daf566f95fc88db3ff37fcec6b6affc49f288b0f7e3b1d8aebd40475f9c902110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53c8039520f039ddf8573d54b13b2ced15beaecf7702a4bb2ea50d66d9a62638 0.600000000000 1403086 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": 944810, "vin": [ { "gen": { "height": 944800 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53c8039520f039ddf8573d54b13b2ced15beaecf7702a4bb2ea50d66d9a62638" } } ], "extra": [ 1, 28, 117, 218, 245, 102, 249, 95, 200, 141, 179, 255, 55, 252, 236, 107, 106, 255, 196, 159, 40, 139, 15, 126, 59, 29, 138, 235, 212, 4, 117, 249, 201, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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