Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df33ed211450b4ee7edb8bd1768fc5fca5c3ed7564cbdd71c007b4faaa1b7bcf

Tx prefix hash: e0c1086b7569bb8868df40dba18cda78e739c81686f63e8f34aa8095a4472e72
Tx public key: a63b69aed1a2e2331cfa1545f94568fb25f5c1e694bd64b0bad9334512889031
Timestamp: 1710824932 Timestamp [UCT]: 2024-03-19 05:08:52 Age [y:d:h:m:s]: 00:295:08:28:46
Block: 981511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211402 RingCT/type: yes/0
Extra: 01a63b69aed1a2e2331cfa1545f94568fb25f5c1e694bd64b0bad933451288903102110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbe0f344b7ede2f52a839ce3135a6a80182645e22c4a5814bd2d197e2c8b43cc 0.600000000000 1441608 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": 981521, "vin": [ { "gen": { "height": 981511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbe0f344b7ede2f52a839ce3135a6a80182645e22c4a5814bd2d197e2c8b43cc" } } ], "extra": [ 1, 166, 59, 105, 174, 209, 162, 226, 51, 28, 250, 21, 69, 249, 69, 104, 251, 37, 245, 193, 230, 148, 189, 100, 176, 186, 217, 51, 69, 18, 136, 144, 49, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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