Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42855540bacb12664e821e70499561e16f4a17055be429490ad27fe636cb5a33

Tx prefix hash: 92996f103f6e77acc789685d21180fb977cd731687102d2cb3d72ea98c298d44
Tx public key: 02de921f8d1f6dcc34d7c6b29b450369d3fa9fd8d13eb8b301d83dd06b2ff42d
Timestamp: 1679468661 Timestamp [UCT]: 2023-03-22 07:04:21 Age [y:d:h:m:s]: 01:342:20:00:42
Block: 722433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505651 RingCT/type: yes/0
Extra: 0102de921f8d1f6dcc34d7c6b29b450369d3fa9fd8d13eb8b301d83dd06b2ff42d021100000002b3164c24000000000000000000

1 output(s) for total of 2.479016716000 dcy

stealth address amount amount idx
00: 40f3c7dfa6af6bd3ab6acc67b720e8b108881981f1771593a5be2bc10ceda6f8 2.479016716000 1167356 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": 722443, "vin": [ { "gen": { "height": 722433 } } ], "vout": [ { "amount": 2479016716, "target": { "key": "40f3c7dfa6af6bd3ab6acc67b720e8b108881981f1771593a5be2bc10ceda6f8" } } ], "extra": [ 1, 2, 222, 146, 31, 141, 31, 109, 204, 52, 215, 198, 178, 155, 69, 3, 105, 211, 250, 159, 216, 209, 62, 184, 179, 1, 216, 61, 208, 107, 47, 244, 45, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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