Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5f2aaa154f9456d8092116ff4d547d50601723f80fc5711d794bb4c3a4360b9

Tx prefix hash: 0c3754477026f10699b41be1d9f483659fde9791c5885aadea8201fd333c9b95
Tx public key: b7ba7fd11644cd27b5b62bf8d1670a43c46f3f7c95a0a72a832b7c4cbd24c981
Timestamp: 1735885663 Timestamp [UCT]: 2025-01-03 06:27:43 Age [y:d:h:m:s]: 00:301:16:00:54
Block: 1189142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213082 RingCT/type: yes/0
Extra: 01b7ba7fd11644cd27b5b62bf8d1670a43c46f3f7c95a0a72a832b7c4cbd24c9810211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2803e31020a39cecc243111d8c37cdcf618cb12626c61c6a7f21a87a779452f5 0.600000000000 1675647 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": 1189152, "vin": [ { "gen": { "height": 1189142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2803e31020a39cecc243111d8c37cdcf618cb12626c61c6a7f21a87a779452f5" } } ], "extra": [ 1, 183, 186, 127, 209, 22, 68, 205, 39, 181, 182, 43, 248, 209, 103, 10, 67, 196, 111, 63, 124, 149, 160, 167, 42, 131, 43, 124, 76, 189, 36, 201, 129, 2, 17, 0, 0, 0, 2, 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