Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 119164b4985f1e98ede3d25ffe200f917c9ec022d8f306c3d5d3a68bcfa7d607

Tx prefix hash: b3d0fbcdae9e27155426238b1befca5776cd9026daa8a8e1c3d2bf7a710efda1
Tx public key: 5ff3007530268c2cd5c9a9ed85f7154ba3ba645f22d03e7f1dca87aac9051a92
Timestamp: 1749663470 Timestamp [UCT]: 2025-06-11 17:37:50 Age [y:d:h:m:s]: 00:158:01:00:35
Block: 1302913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110649 RingCT/type: yes/0
Extra: 015ff3007530268c2cd5c9a9ed85f7154ba3ba645f22d03e7f1dca87aac9051a9202110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86efb0607bbae1518a3400e5af315493bfc2f2132842717e43fc7e989f5f9b91 0.600000000000 1790488 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": 1302923, "vin": [ { "gen": { "height": 1302913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86efb0607bbae1518a3400e5af315493bfc2f2132842717e43fc7e989f5f9b91" } } ], "extra": [ 1, 95, 243, 0, 117, 48, 38, 140, 44, 213, 201, 169, 237, 133, 247, 21, 75, 163, 186, 100, 95, 34, 208, 62, 127, 29, 202, 135, 170, 201, 5, 26, 146, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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