Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2714bcb5f4214c9d2e0cc880a066baa601a5b8cc370da08821acf071c4c4bae6

Tx prefix hash: 3f7751b63a20dce3eca79c698670f3d1607b373d18f71f837a1f634942e34a9f
Tx public key: f0ff26e5fb82cf65caa9954bc023276d4a011255e8d90a838dad8fa331c47b52
Timestamp: 1749744418 Timestamp [UCT]: 2025-06-12 16:06:58 Age [y:d:h:m:s]: 00:152:19:03:48
Block: 1303555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106918 RingCT/type: yes/0
Extra: 01f0ff26e5fb82cf65caa9954bc023276d4a011255e8d90a838dad8fa331c47b520211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c8b4e676620eb4612cf0d72ac1cf94fcfabb020a7ce6779d1b9f5f083f1bb2a 0.600000000000 1791138 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": 1303565, "vin": [ { "gen": { "height": 1303555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c8b4e676620eb4612cf0d72ac1cf94fcfabb020a7ce6779d1b9f5f083f1bb2a" } } ], "extra": [ 1, 240, 255, 38, 229, 251, 130, 207, 101, 202, 169, 149, 75, 192, 35, 39, 109, 74, 1, 18, 85, 232, 217, 10, 131, 141, 173, 143, 163, 49, 196, 123, 82, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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