Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c71d065821a778c38d963ecf07d3d4eb8a5670638adb04ce03820f5da38cc1e

Tx prefix hash: a150943071aee1745fce246a1e81f0624ad277e199136b469e573d630d5fb8e1
Tx public key: c14b78d2d3594b2cd86999e88cb0ceed0d046d395fd3fece3d04460cf9d28743
Timestamp: 1757425538 Timestamp [UCT]: 2025-09-09 13:45:38 Age [y:d:h:m:s]: 00:143:14:06:01
Block: 1364754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102597 RingCT/type: yes/0
Extra: 01c14b78d2d3594b2cd86999e88cb0ceed0d046d395fd3fece3d04460cf9d28743021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e82c5620408a5e7f96d40960b9b34ecde69751c4585bd41b7d19b02bc771ad6 0.600000000000 1852793 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": 1364764, "vin": [ { "gen": { "height": 1364754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e82c5620408a5e7f96d40960b9b34ecde69751c4585bd41b7d19b02bc771ad6" } } ], "extra": [ 1, 193, 75, 120, 210, 211, 89, 75, 44, 216, 105, 153, 232, 140, 176, 206, 237, 13, 4, 109, 57, 95, 211, 254, 206, 61, 4, 70, 12, 249, 210, 135, 67, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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