Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51271a8e4f8c647256365903a11cc52c86a460a4d86b5ce01a33b2bdf1f40d55

Tx prefix hash: f78f34de3063559a47b08e3a6f56848986c53678a00b5677226f66f53c90acc1
Tx public key: 104f0eab158c40f217a77c826b3a75c796374fed98a450aa3414fb0b82cd92ce
Timestamp: 1746112643 Timestamp [UCT]: 2025-05-01 15:17:23 Age [y:d:h:m:s]: 00:196:22:23:28
Block: 1273520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138459 RingCT/type: yes/0
Extra: 01104f0eab158c40f217a77c826b3a75c796374fed98a450aa3414fb0b82cd92ce021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b76ea0068c6a837af2c2b034e64d5c232a4c32e7010af54c40c3fdfcdb8fcc77 0.600000000000 1760803 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": 1273530, "vin": [ { "gen": { "height": 1273520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b76ea0068c6a837af2c2b034e64d5c232a4c32e7010af54c40c3fdfcdb8fcc77" } } ], "extra": [ 1, 16, 79, 14, 171, 21, 140, 64, 242, 23, 167, 124, 130, 107, 58, 117, 199, 150, 55, 79, 237, 152, 164, 80, 170, 52, 20, 251, 11, 130, 205, 146, 206, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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