Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81a51b638a14046a1afcbef09b914ab468a3eaa8afa29e8f7b5402b3a54bf478

Tx prefix hash: f7ff6ead959d07f197e222d510cc9b6ce2db0d471014682d49d81a1dccd8f88d
Tx public key: c22f7fae70c871527286b8e55adffaeb279f98c228543d7f8db3048bda7fbb90
Timestamp: 1717763876 Timestamp [UCT]: 2024-06-07 12:37:56 Age [y:d:h:m:s]: 00:146:04:55:45
Block: 1039022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104640 RingCT/type: yes/0
Extra: 01c22f7fae70c871527286b8e55adffaeb279f98c228543d7f8db3048bda7fbb900211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8edd9cbfcdbe98a3769e45016a5b9a0843060595a4bbb2965b6ede51f59e6e7c 0.600000000000 1507605 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": 1039032, "vin": [ { "gen": { "height": 1039022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8edd9cbfcdbe98a3769e45016a5b9a0843060595a4bbb2965b6ede51f59e6e7c" } } ], "extra": [ 1, 194, 47, 127, 174, 112, 200, 113, 82, 114, 134, 184, 229, 90, 223, 250, 235, 39, 159, 152, 194, 40, 84, 61, 127, 141, 179, 4, 139, 218, 127, 187, 144, 2, 17, 0, 0, 0, 1, 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