Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9bd2b3aa8973316d703c0a0a507702287e57f52049cf3351892e008895773b2

Tx prefix hash: 55389b98c70d5c4b073e45ca78a233879b7270edb4a652f504ede716a618c8ea
Tx public key: 5541b714c2c827bddf629ad507e3772129eb9b9aaaf08a10413149eb6b0deaa9
Timestamp: 1725161775 Timestamp [UCT]: 2024-09-01 03:36:15 Age [y:d:h:m:s]: 00:293:14:54:58
Block: 1100343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209587 RingCT/type: yes/0
Extra: 015541b714c2c827bddf629ad507e3772129eb9b9aaaf08a10413149eb6b0deaa9021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f73a5c7f189018c3c7a3fdf75e147a48f64bd68e258c263ecd59af5815561004 0.600000000000 1576320 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": 1100353, "vin": [ { "gen": { "height": 1100343 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f73a5c7f189018c3c7a3fdf75e147a48f64bd68e258c263ecd59af5815561004" } } ], "extra": [ 1, 85, 65, 183, 20, 194, 200, 39, 189, 223, 98, 154, 213, 7, 227, 119, 33, 41, 235, 155, 154, 170, 240, 138, 16, 65, 49, 73, 235, 107, 13, 234, 169, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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