Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9180c2986bdf4262e3d924787a85583b6b2f70f0262291e7bb83731a151fd7e1

Tx prefix hash: 44c22a1704bb999e4d2fbce85fb4e3ce366b59ed7f40540927cc17baa6e79181
Tx public key: be2dedee41b731f8c915f41e864941928ed201b4790c7d6ddf31311a5c60f7fd
Timestamp: 1736855780 Timestamp [UCT]: 2025-01-14 11:56:20 Age [y:d:h:m:s]: 00:155:11:54:53
Block: 1197150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110826 RingCT/type: yes/0
Extra: 01be2dedee41b731f8c915f41e864941928ed201b4790c7d6ddf31311a5c60f7fd0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff6916fab9c974b81b138ace923c6e68f70bb9840c4ba9e0584b915c0536bb65 0.600000000000 1683757 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": 1197160, "vin": [ { "gen": { "height": 1197150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff6916fab9c974b81b138ace923c6e68f70bb9840c4ba9e0584b915c0536bb65" } } ], "extra": [ 1, 190, 45, 237, 238, 65, 183, 49, 248, 201, 21, 244, 30, 134, 73, 65, 146, 142, 210, 1, 180, 121, 12, 125, 109, 223, 49, 49, 26, 92, 96, 247, 253, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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