Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4724775cf360f26e7f26de7ca16c3df8b72b7988a87c4280cebe55e3703838b1

Tx prefix hash: 882b0f3095e5417a1681853aecf912e9aaa7d6424127782bfca84b124b8bdeba
Tx public key: c079522b6d39d5eff78f4ef630e6115fb3e401a9ff49d79224ae1fc225626b49
Timestamp: 1717466943 Timestamp [UCT]: 2024-06-04 02:09:03 Age [y:d:h:m:s]: 01:182:22:46:16
Block: 1036562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389355 RingCT/type: yes/0
Extra: 01c079522b6d39d5eff78f4ef630e6115fb3e401a9ff49d79224ae1fc225626b490211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02350ba9c210632847cfb84f9ccb01bfaf3ccccfb4e6e42270a4b5fe7540b36c 0.600000000000 1505089 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": 1036572, "vin": [ { "gen": { "height": 1036562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02350ba9c210632847cfb84f9ccb01bfaf3ccccfb4e6e42270a4b5fe7540b36c" } } ], "extra": [ 1, 192, 121, 82, 43, 109, 57, 213, 239, 247, 143, 78, 246, 48, 230, 17, 95, 179, 228, 1, 169, 255, 73, 215, 146, 36, 174, 31, 194, 37, 98, 107, 73, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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