Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8b51adf09d71bf26dc11795b1c2a7942f9f24acd5ab1e7313a786030a3aff81

Tx prefix hash: fda6e6837cec96162e325d47d31e712f5895b6285e13890fe99875522c8e7ded
Tx public key: cb1cfa2f54a8b99a1326a08bd13ca89e722b395e5346c1fbe349466f8c79e309
Timestamp: 1726610028 Timestamp [UCT]: 2024-09-17 21:53:48 Age [y:d:h:m:s]: 00:058:05:11:37
Block: 1112347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41609 RingCT/type: yes/0
Extra: 01cb1cfa2f54a8b99a1326a08bd13ca89e722b395e5346c1fbe349466f8c79e30902110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdde021e42cdf090a1805f8e6d246a059cfb6c40fc6850e1ca50d01a96b0cdd5 0.600000000000 1591638 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": 1112357, "vin": [ { "gen": { "height": 1112347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdde021e42cdf090a1805f8e6d246a059cfb6c40fc6850e1ca50d01a96b0cdd5" } } ], "extra": [ 1, 203, 28, 250, 47, 84, 168, 185, 154, 19, 38, 160, 139, 209, 60, 168, 158, 114, 43, 57, 94, 83, 70, 193, 251, 227, 73, 70, 111, 140, 121, 227, 9, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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