Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c893fc2e08739004dc9081883e0bb6c720baeb1e7d9dc4e4f01f8a2252c81942

Tx prefix hash: 7dbcd3d58bf44dccfb4d19fe1c63aad7094cc72a432a68e019f5a58bd83cd31a
Tx public key: 2646c01ec7f58cbabca0e83d0d2e262a65b490de7267787d4ab046379cbec352
Timestamp: 1634999528 Timestamp [UCT]: 2021-10-23 14:32:08 Age [y:d:h:m:s]: 03:066:13:19:19
Block: 358863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 825882 RingCT/type: yes/0
Extra: 012646c01ec7f58cbabca0e83d0d2e262a65b490de7267787d4ab046379cbec35202110000000106faf294000000000000000000

1 output(s) for total of 39.713514341000 dcy

stealth address amount amount idx
00: f094ff51a8598bc62ae3faa19b667ed68a1a3a39f55eaa0465138d61d6691d17 39.713514341000 731028 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": 358873, "vin": [ { "gen": { "height": 358863 } } ], "vout": [ { "amount": 39713514341, "target": { "key": "f094ff51a8598bc62ae3faa19b667ed68a1a3a39f55eaa0465138d61d6691d17" } } ], "extra": [ 1, 38, 70, 192, 30, 199, 245, 140, 186, 188, 160, 232, 61, 13, 46, 38, 42, 101, 180, 144, 222, 114, 103, 120, 125, 74, 176, 70, 55, 156, 190, 195, 82, 2, 17, 0, 0, 0, 1, 6, 250, 242, 148, 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