Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bda0b20440e942a95089014edcf6c1b1495dc2d6fc24c8a69db3e7ca41ed080d

Tx prefix hash: f95916ab1223cef6c61f1f4ad526fbe9ad3e7037645c168abc217818535869d9
Tx public key: 4009546be16376e998d0479d42a544148971249f8f072b9a0f5443cee3b623a5
Timestamp: 1766089031 Timestamp [UCT]: 2025-12-18 20:17:11 Age [y:d:h:m:s]: 00:003:08:10:57
Block: 1436518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2393 RingCT/type: yes/0
Extra: 014009546be16376e998d0479d42a544148971249f8f072b9a0f5443cee3b623a5021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aeb59f7de8eb0b85e5a41b6524b84914b5a6677ed7b2e6520bf3a0dc07a0988a 0.600000000000 1925323 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": 1436528, "vin": [ { "gen": { "height": 1436518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aeb59f7de8eb0b85e5a41b6524b84914b5a6677ed7b2e6520bf3a0dc07a0988a" } } ], "extra": [ 1, 64, 9, 84, 107, 225, 99, 118, 233, 152, 208, 71, 157, 66, 165, 68, 20, 137, 113, 36, 159, 143, 7, 43, 154, 15, 84, 67, 206, 227, 182, 35, 165, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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