Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd34a0cf7c2a0ada8a2677f7bc33f735d25ee0d8a94fe9cf0dac4c111f54ac9e

Tx prefix hash: 1c6f0e6359634197f5e83f0381939144ff45e0a41a915740d9e067c7ac544e82
Tx public key: 5d2eec867c300037054a6f78605b89b0c0a4901759f2cbeaf369075614d3b798
Timestamp: 1673298884 Timestamp [UCT]: 2023-01-09 21:14:44 Age [y:d:h:m:s]: 01:310:05:08:24
Block: 671237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482694 RingCT/type: yes/0
Extra: 015d2eec867c300037054a6f78605b89b0c0a4901759f2cbeaf369075614d3b79802110000000152542ceb000000000000000000

1 output(s) for total of 3.663642857000 dcy

stealth address amount amount idx
00: b9f2b6bbb6697c6e24157164eb231cbd2072da5a537b1bfd2be424ed1c8045e8 3.663642857000 1112696 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": 671247, "vin": [ { "gen": { "height": 671237 } } ], "vout": [ { "amount": 3663642857, "target": { "key": "b9f2b6bbb6697c6e24157164eb231cbd2072da5a537b1bfd2be424ed1c8045e8" } } ], "extra": [ 1, 93, 46, 236, 134, 124, 48, 0, 55, 5, 74, 111, 120, 96, 91, 137, 176, 192, 164, 144, 23, 89, 242, 203, 234, 243, 105, 7, 86, 20, 211, 183, 152, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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