Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6d22dfc17993b8fb1207788a8a245e56c2d529001c65f5a2e17aaaa9f74b966

Tx prefix hash: 07a14822045c99e02da33992369a5473436f77be1747ed82a762d04441babbbd
Tx public key: 647270dc6a8ef6bf166f902d95e5b3e1ed99bd2eaf52f4f3af59f4fabd44f68c
Timestamp: 1708860307 Timestamp [UCT]: 2024-02-25 11:25:07 Age [y:d:h:m:s]: 01:051:06:23:01
Block: 965208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297654 RingCT/type: yes/0
Extra: 01647270dc6a8ef6bf166f902d95e5b3e1ed99bd2eaf52f4f3af59f4fabd44f68c02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21d38dff749200c1a87b63c6b5f71b0dcbe732891210b68cda498c04a7cb3bee 0.600000000000 1424957 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": 965218, "vin": [ { "gen": { "height": 965208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21d38dff749200c1a87b63c6b5f71b0dcbe732891210b68cda498c04a7cb3bee" } } ], "extra": [ 1, 100, 114, 112, 220, 106, 142, 246, 191, 22, 111, 144, 45, 149, 229, 179, 225, 237, 153, 189, 46, 175, 82, 244, 243, 175, 89, 244, 250, 189, 68, 246, 140, 2, 17, 0, 0, 0, 10, 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