Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b85e0c9a2bb1dd13c3da82fbf7d24fa051e43127e2a2260f8e1bbc21242646f

Tx prefix hash: 7a63aac982658a8657cbc1f8dd0e6e5bcf54f90a012c5fe2ceee8b51586d4846
Tx public key: 5bdad9b1e434ac63190a6ac2a722c7bfaebfc3a7f1653331a40436de74f597b9
Timestamp: 1731922143 Timestamp [UCT]: 2024-11-18 09:29:03 Age [y:d:h:m:s]: 00:145:20:55:49
Block: 1156301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104075 RingCT/type: yes/0
Extra: 015bdad9b1e434ac63190a6ac2a722c7bfaebfc3a7f1653331a40436de74f597b9021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1dfebc4cfb75a82a2d74982734d7113a5a36024755f6176d78de0fcacdb58c1 0.600000000000 1641924 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": 1156311, "vin": [ { "gen": { "height": 1156301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1dfebc4cfb75a82a2d74982734d7113a5a36024755f6176d78de0fcacdb58c1" } } ], "extra": [ 1, 91, 218, 217, 177, 228, 52, 172, 99, 25, 10, 106, 194, 167, 34, 199, 191, 174, 191, 195, 167, 241, 101, 51, 49, 164, 4, 54, 222, 116, 245, 151, 185, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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