Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15b5cb97361c71e1eaffb28bfffee1ad2b5a8879306d5be593ec989a7bb7cbc8

Tx prefix hash: d263e1a064a8140f295c1b3aa41b68bc8fcf6ddcc944de6503a3758b6bd02cee
Tx public key: 53b008e5dff3ba40793092c760564b6658c0b39cc71c99b2e4796f267d2da750
Timestamp: 1756093793 Timestamp [UCT]: 2025-08-25 03:49:53 Age [y:d:h:m:s]: 00:155:17:28:48
Block: 1353869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111147 RingCT/type: yes/0
Extra: 0153b008e5dff3ba40793092c760564b6658c0b39cc71c99b2e4796f267d2da7500211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12a1b9f8a9b4fdccbf1d9af24afb54c0ad42db1a83b9221fed6e0ab77fe41c46 0.600000000000 1841848 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": 1353879, "vin": [ { "gen": { "height": 1353869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12a1b9f8a9b4fdccbf1d9af24afb54c0ad42db1a83b9221fed6e0ab77fe41c46" } } ], "extra": [ 1, 83, 176, 8, 229, 223, 243, 186, 64, 121, 48, 146, 199, 96, 86, 75, 102, 88, 192, 179, 156, 199, 28, 153, 178, 228, 121, 111, 38, 125, 45, 167, 80, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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