Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cd5cefeb323f4c4165f4a94c0bca4c088667af492a2524a06526039a8cb768c

Tx prefix hash: 8fe56628ee409c218407c7f026793584c5e2db1981a3c7b1ec79e3548c6ad404
Tx public key: e4219c3e379263b58b5ea838d101ec851f76a5bf0527c341a6461538406112c9
Timestamp: 1764543826 Timestamp [UCT]: 2025-11-30 23:03:46 Age [y:d:h:m:s]: 00:038:19:50:56
Block: 1423720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27799 RingCT/type: yes/0
Extra: 01e4219c3e379263b58b5ea838d101ec851f76a5bf0527c341a6461538406112c90211000000024e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffcccba2f3c18e7b0d7ba9cec1644b5cd2acb5b5d840bb2ad89bccb294f77a95 0.600000000000 1912341 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": 1423730, "vin": [ { "gen": { "height": 1423720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffcccba2f3c18e7b0d7ba9cec1644b5cd2acb5b5d840bb2ad89bccb294f77a95" } } ], "extra": [ 1, 228, 33, 156, 62, 55, 146, 99, 181, 139, 94, 168, 56, 209, 1, 236, 133, 31, 118, 165, 191, 5, 39, 195, 65, 166, 70, 21, 56, 64, 97, 18, 201, 2, 17, 0, 0, 0, 2, 78, 123, 252, 9, 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