Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd6f5a5aa2cd832cf2e43981d4eeac831f35b4449b361196ad90fe624bcbbc7e

Tx prefix hash: dd667f98388dd7b474f1f3b1304166c16a76b1047138826f2c7a57dcde1f485f
Tx public key: 93e15ecd39ed30958b29691609b8231e67b617a914f07cdb7d610539c6bbc0a8
Timestamp: 1735791558 Timestamp [UCT]: 2025-01-02 04:19:18 Age [y:d:h:m:s]: 00:170:02:20:26
Block: 1188339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121234 RingCT/type: yes/0
Extra: 0193e15ecd39ed30958b29691609b8231e67b617a914f07cdb7d610539c6bbc0a8021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bda3e33af90cbe7793a220ad67f8f352676f07cf6082d8fbafa9738222c2de7 0.600000000000 1674840 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": 1188349, "vin": [ { "gen": { "height": 1188339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bda3e33af90cbe7793a220ad67f8f352676f07cf6082d8fbafa9738222c2de7" } } ], "extra": [ 1, 147, 225, 94, 205, 57, 237, 48, 149, 139, 41, 105, 22, 9, 184, 35, 30, 103, 182, 23, 169, 20, 240, 124, 219, 125, 97, 5, 57, 198, 187, 192, 168, 2, 17, 0, 0, 0, 4, 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