Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a6ae2a4c4f4669bcf6dfbcc830a0722f0f56a7247d36e79ebee0e8db8755d36

Tx prefix hash: 6b4c5e70c5000532a49cea8e19ec6dae9f8a40cfc5ba07bcf19f4b503d00fab1
Tx public key: 425145c9bf63036d47626c440abb399949ac34f6315b346c6879e23430e56c1e
Timestamp: 1745792288 Timestamp [UCT]: 2025-04-27 22:18:08 Age [y:d:h:m:s]: 00:011:03:46:32
Block: 1270874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7971 RingCT/type: yes/0
Extra: 01425145c9bf63036d47626c440abb399949ac34f6315b346c6879e23430e56c1e0211000000051f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02aa04806706d52543826118595d9c169fa9bddd3a448747b274a1d2a2f4040d 0.600000000000 1758119 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": 1270884, "vin": [ { "gen": { "height": 1270874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02aa04806706d52543826118595d9c169fa9bddd3a448747b274a1d2a2f4040d" } } ], "extra": [ 1, 66, 81, 69, 201, 191, 99, 3, 109, 71, 98, 108, 68, 10, 187, 57, 153, 73, 172, 52, 246, 49, 91, 52, 108, 104, 121, 226, 52, 48, 229, 108, 30, 2, 17, 0, 0, 0, 5, 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