Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcfff88acc5d4977aab0ef0c3a039e2cf7b5f040fc5fabe1292f689645a5677c

Tx prefix hash: 8d0c0dec91e4f2dc7d06b69205dbf796aada9dd7b90237bcc023ec89de09c1d5
Tx public key: 89aa4c8c644da65721a6c4de0efb09c79c8043f000dd0643e51d151d8dd7a881
Timestamp: 1749901315 Timestamp [UCT]: 2025-06-14 11:41:55 Age [y:d:h:m:s]: 00:160:11:48:18
Block: 1304825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112453 RingCT/type: yes/0
Extra: 0189aa4c8c644da65721a6c4de0efb09c79c8043f000dd0643e51d151d8dd7a881021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 375311ba84a03204052dc4e30049fc8ca1e87c129de55030afa90d6f2aac7e73 0.600000000000 1792418 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": 1304835, "vin": [ { "gen": { "height": 1304825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "375311ba84a03204052dc4e30049fc8ca1e87c129de55030afa90d6f2aac7e73" } } ], "extra": [ 1, 137, 170, 76, 140, 100, 77, 166, 87, 33, 166, 196, 222, 14, 251, 9, 199, 156, 128, 67, 240, 0, 221, 6, 67, 229, 29, 21, 29, 141, 215, 168, 129, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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