Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 451efc40cb87c97de01e9ccaf91bcbea7a0f1ce418f9a7232cae1eeea7201104

Tx prefix hash: 19b890f6d91acb2689b6751436eb10e9265740ffb3214f696b154d23e2102708
Tx public key: ceeb756fc00e18edfb175cdee9d5f5511b22fe8c4bfd0a68011b4fef4c89df04
Timestamp: 1710533467 Timestamp [UCT]: 2024-03-15 20:11:07 Age [y:d:h:m:s]: 00:257:18:34:11
Block: 979091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184535 RingCT/type: yes/0
Extra: 01ceeb756fc00e18edfb175cdee9d5f5511b22fe8c4bfd0a68011b4fef4c89df040211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9534d7c680599e16f49c95977b91038c7a6776c8aa954a2e5632ef92e68a6f6a 0.600000000000 1439122 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": 979101, "vin": [ { "gen": { "height": 979091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9534d7c680599e16f49c95977b91038c7a6776c8aa954a2e5632ef92e68a6f6a" } } ], "extra": [ 1, 206, 235, 117, 111, 192, 14, 24, 237, 251, 23, 92, 222, 233, 213, 245, 81, 27, 34, 254, 140, 75, 253, 10, 104, 1, 27, 79, 239, 76, 137, 223, 4, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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