Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db0f89182563f24d9c28aacf05b2b2c4b02581a529274f8f23d6793c7a54cfd2

Tx prefix hash: 58d81da1fd41aefa06a23152e6572501b2c193388b2476b8431bd7cb402c885b
Tx public key: 861729467eb343d5b57ea43aee60b02535d93268a97b08a969046f21dadfdfe3
Timestamp: 1735705931 Timestamp [UCT]: 2025-01-01 04:32:11 Age [y:d:h:m:s]: 00:170:20:47:19
Block: 1187627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121796 RingCT/type: yes/0
Extra: 01861729467eb343d5b57ea43aee60b02535d93268a97b08a969046f21dadfdfe3021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6fada0f406fae965614ab3b26a71e4b76838a2a3ff2874f5a75ecc26d232ff0 0.600000000000 1674120 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": 1187637, "vin": [ { "gen": { "height": 1187627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6fada0f406fae965614ab3b26a71e4b76838a2a3ff2874f5a75ecc26d232ff0" } } ], "extra": [ 1, 134, 23, 41, 70, 126, 179, 67, 213, 181, 126, 164, 58, 238, 96, 176, 37, 53, 217, 50, 104, 169, 123, 8, 169, 105, 4, 111, 33, 218, 223, 223, 227, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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