Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b85f3cca6d729bb965d2f4d9a8684eef88602c0275600400258c6033b28ad925

Tx prefix hash: 31c2a40f3fdd0a960cc7a6c202447d62a1b4cb6a7fc023ebf413f4806ebcce32
Tx public key: 7f39a0baf8d3b99f7acaadfae187dfe2071ae8f9927da5f13364c4a0bc521220
Timestamp: 1746809366 Timestamp [UCT]: 2025-05-09 16:49:26 Age [y:d:h:m:s]: 00:195:05:37:18
Block: 1279280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137250 RingCT/type: yes/0
Extra: 017f39a0baf8d3b99f7acaadfae187dfe2071ae8f9927da5f13364c4a0bc5212200211000000071f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7790e9459ae705398b00d4f258276654cf9fe04d276d3fb04e77f50590e4d0ef 0.600000000000 1766655 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": 1279290, "vin": [ { "gen": { "height": 1279280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7790e9459ae705398b00d4f258276654cf9fe04d276d3fb04e77f50590e4d0ef" } } ], "extra": [ 1, 127, 57, 160, 186, 248, 211, 185, 159, 122, 202, 173, 250, 225, 135, 223, 226, 7, 26, 232, 249, 146, 125, 165, 241, 51, 100, 196, 160, 188, 82, 18, 32, 2, 17, 0, 0, 0, 7, 31, 144, 81, 122, 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