Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 649d17f9a48eb73daffc7e142acd9df2b1a7310153cb1710a5780c86306f7060

Tx prefix hash: d24f84b97b42fee4d98a93f801e9930f0430e8902d42422cb986d493079d6685
Tx public key: be831180db4eea9bb7b6982c5c72812a6ca83ead34f6133c143daa433516fa09
Timestamp: 1712913048 Timestamp [UCT]: 2024-04-12 09:10:48 Age [y:d:h:m:s]: 00:318:21:55:42
Block: 998785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227983 RingCT/type: yes/0
Extra: 01be831180db4eea9bb7b6982c5c72812a6ca83ead34f6133c143daa433516fa0902110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f18929f09ce8dc6c2a8633d4f4f7c63e09d1cc4d53711d70d260db103e57a7e6 0.600000000000 1459243 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": 998795, "vin": [ { "gen": { "height": 998785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f18929f09ce8dc6c2a8633d4f4f7c63e09d1cc4d53711d70d260db103e57a7e6" } } ], "extra": [ 1, 190, 131, 17, 128, 219, 78, 234, 155, 183, 182, 152, 44, 92, 114, 129, 42, 108, 168, 62, 173, 52, 246, 19, 60, 20, 61, 170, 67, 53, 22, 250, 9, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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