Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fec453f476b646b5d986b7beb3ab9af29bddf16a56671dda5a4a97c993cf26ac

Tx prefix hash: db4d5468929376388f7e97bb8be15441d11734466b945660da703d05096c9cab
Tx public key: db58a3dd876b44e4ef1a0b8d8d4999a4596994f66a512163f7b03afd3d530328
Timestamp: 1711112056 Timestamp [UCT]: 2024-03-22 12:54:16 Age [y:d:h:m:s]: 01:014:03:09:04
Block: 983890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271054 RingCT/type: yes/0
Extra: 01db58a3dd876b44e4ef1a0b8d8d4999a4596994f66a512163f7b03afd3d53032802110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff3f64f8641c43aa374c75bee7733d8db286f5a51cce1cf752303e9489c8f4b6 0.600000000000 1444043 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": 983900, "vin": [ { "gen": { "height": 983890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff3f64f8641c43aa374c75bee7733d8db286f5a51cce1cf752303e9489c8f4b6" } } ], "extra": [ 1, 219, 88, 163, 221, 135, 107, 68, 228, 239, 26, 11, 141, 141, 73, 153, 164, 89, 105, 148, 246, 106, 81, 33, 99, 247, 176, 58, 253, 61, 83, 3, 40, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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