Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c623fe5edcc2b48327feadead1eabab0c01b6e36ebe3aba1b042b41657e4070b

Tx prefix hash: 5a4a9d12e04e082f878940933ab4ee537053a4470be6629da5c31663a20ca47a
Tx public key: a0cab0fb7caaa2259b7eb71362c6bc00c99c61a08f4ce1952bd18ceda177e8e5
Timestamp: 1735495686 Timestamp [UCT]: 2024-12-29 18:08:06 Age [y:d:h:m:s]: 00:170:12:49:02
Block: 1185886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121606 RingCT/type: yes/0
Extra: 01a0cab0fb7caaa2259b7eb71362c6bc00c99c61a08f4ce1952bd18ceda177e8e50211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31aa0cb64dd74d8656f15cd6e774395521a9b1dca9b95158f5c6fe72d66e0185 0.600000000000 1672361 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": 1185896, "vin": [ { "gen": { "height": 1185886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31aa0cb64dd74d8656f15cd6e774395521a9b1dca9b95158f5c6fe72d66e0185" } } ], "extra": [ 1, 160, 202, 176, 251, 124, 170, 162, 37, 155, 126, 183, 19, 98, 198, 188, 0, 201, 156, 97, 160, 143, 76, 225, 149, 43, 209, 140, 237, 161, 119, 232, 229, 2, 17, 0, 0, 0, 6, 31, 10, 83, 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