Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9043f238d6016a6527b1b3a539c831125a31e0ec67fce1a71f52be589132503

Tx prefix hash: 256aa46fe8e623b6f6c1be74490b090dc5513be2622ce8ab0b28a028f55f9edc
Tx public key: edc855a0d4daf3760e0db47aa84f29443abea83ae81f41506efb4b7c7a7cd6a3
Timestamp: 1675474295 Timestamp [UCT]: 2023-02-04 01:31:35 Age [y:d:h:m:s]: 01:351:09:44:52
Block: 689297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 512081 RingCT/type: yes/0
Extra: 01edc855a0d4daf3760e0db47aa84f29443abea83ae81f41506efb4b7c7a7cd6a302110000000274b6d784000000000000000000

1 output(s) for total of 3.192073091000 dcy

stealth address amount amount idx
00: dd6b13b47e927df4d70b61878a7189b048b83c75862c5cd1ba7137d62b5ed7fd 3.192073091000 1131965 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": 689307, "vin": [ { "gen": { "height": 689297 } } ], "vout": [ { "amount": 3192073091, "target": { "key": "dd6b13b47e927df4d70b61878a7189b048b83c75862c5cd1ba7137d62b5ed7fd" } } ], "extra": [ 1, 237, 200, 85, 160, 212, 218, 243, 118, 14, 13, 180, 122, 168, 79, 41, 68, 58, 190, 168, 58, 232, 31, 65, 80, 110, 251, 75, 124, 122, 124, 214, 163, 2, 17, 0, 0, 0, 2, 116, 182, 215, 132, 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