Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7ab74144d9e95f711d4c65a6249ca123446532bf7a4e7cd3401f3a481b3564f

Tx prefix hash: 0f367a277194a7934409506924f7df797ac6fec20e9f12b0478235bea87d316f
Tx public key: 792a66e2e1a3158be85abab3e133261e3f3f88c80524184e6008d59afd7f264b
Timestamp: 1703067597 Timestamp [UCT]: 2023-12-20 10:19:57 Age [y:d:h:m:s]: 01:129:13:43:21
Block: 917173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353755 RingCT/type: yes/0
Extra: 01792a66e2e1a3158be85abab3e133261e3f3f88c80524184e6008d59afd7f264b021100000002e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 407efc08e79a468bc4643778ba68c510c163aeb1b07f6f3d20a2161e1539264c 0.600000000000 1374743 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": 917183, "vin": [ { "gen": { "height": 917173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "407efc08e79a468bc4643778ba68c510c163aeb1b07f6f3d20a2161e1539264c" } } ], "extra": [ 1, 121, 42, 102, 226, 225, 163, 21, 139, 232, 90, 186, 179, 225, 51, 38, 30, 63, 63, 136, 200, 5, 36, 24, 78, 96, 8, 213, 154, 253, 127, 38, 75, 2, 17, 0, 0, 0, 2, 228, 187, 107, 131, 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