Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ad4d3468855111a1daf23e1c6f845f1deb42807e37422618a2a9b6f90552033

Tx prefix hash: f625b567f2ffd3a6d0ab4adfcae97e94eda0467c8b6299610758877bf3e3ba17
Tx public key: 702f83bb42e593cb4360f68dd4904d746e7742edc295daab34ed4698401b8526
Timestamp: 1701690045 Timestamp [UCT]: 2023-12-04 11:40:45 Age [y:d:h:m:s]: 01:135:12:55:57
Block: 905751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358021 RingCT/type: yes/0
Extra: 01702f83bb42e593cb4360f68dd4904d746e7742edc295daab34ed4698401b85260211000000014b8f5122000000000000000000

1 output(s) for total of 0.612168413000 dcy

stealth address amount amount idx
00: 527b6886bce1b0e654e2325c218bcc98fc5448a72b0fe9b6cdd0533562a24376 0.612168413000 1362666 of 0

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": 905761, "vin": [ { "gen": { "height": 905751 } } ], "vout": [ { "amount": 612168413, "target": { "key": "527b6886bce1b0e654e2325c218bcc98fc5448a72b0fe9b6cdd0533562a24376" } } ], "extra": [ 1, 112, 47, 131, 187, 66, 229, 147, 203, 67, 96, 246, 141, 212, 144, 77, 116, 110, 119, 66, 237, 194, 149, 218, 171, 52, 237, 70, 152, 64, 27, 133, 38, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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